-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add fuzzing target to fuzz return type and parameters #301
Conversation
77945b3
to
fcb0862
Compare
b2d86f7
to
42f6f6c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Good work on improving the verifications we do on the changes.
e4443f9
to
2e2c893
Compare
I removed the fuzz check temporarily, once this merges let me know and I will add the 2 new ones |
guest and host function calls. Rename existing target to host_print. Move fuzz directory to root directory. Signed-off-by: Ludvig Liljenberg <lliljenberg@microsoft.com>
Signed-off-by: Ludvig Liljenberg <lliljenberg@microsoft.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
host_print
.host_call
fuzz target found, where RSP kept decreasing after each dispatch, and eventually caused an error. RSP should be reset every dispatch. The new logic resets RSP before each dispatch to the original RSP (which points to beginning of stack). I applied the new logic to all 3 drivers, even though the bug only manifested on KVM.In order to merge this PR, we need to remove
fuzz/fuzzing
status check from branch protection, as this PR changes the name of that job tofuzz/fuzzing (guest_call)
andfuzz/fuzzing (host_print)